Sams Teach Yourself MCSE Windows NT Server 4 in 14 Days
(Publisher: Macmillan Computer Publishing)
Author(s): David Schaer, et al
ISBN: 0672311283
Publication Date: 12/15/97

Chapter 3
Installing NT Server 4.0

by David Schaer and Theresa Hadden

3.1. Overview

Questions about installing NT Server can be as basic as reviewing your knowledge of hardware requirements to as complex as questions on automated setup options. This chapter guides you through each step of the installation and upgrade process of NT Server 4.0. The questions that follow act as a review on areas of installation, upgrades, and operating system coexistence.

This chapter leads you through the multiple phases of an NT installation. The exam tests your ability to select equipment that is capable of running NT Server 4.0, install it both locally and from across the network, upgrade it from previous operating systems, and troubleshoot common installation problems.

3.1.1. Objectives

The information in this chapter provides a basis for properly understanding how to install Windows NT. The following Microsoft objectives as stated in the Preparation Guide are addressed in this chapter:

•  Choose a protocol for various situations.

•  Install, configure, and troubleshoot various protocols including TCP/IP, NWLink, and NetBEUI.

•  Install Windows NT Server on Intel-based platforms.

•  Install Windows NT to perform various server roles including primary domain controller, backup domain controller, member server, and stand-alone server.

•  Install Windows NT using various methods including CD-ROM and over the network, and by using Network Client Administrator.

•  Configure protocols and protocol bindings.

•  Configure network adapters.

•  Choose the appropriate course of action to take to resolve installation failures.

3.1.2. Fast Facts

The following list of facts is a concise picture of the information presented in this chapter. It acts as both an overview for the chapter and as a study aid to help you do any last-minute cramming.

•  Minimum requirement for NT Server 4.0 is 486DX/33, 12MB RAM (16MB RAM is recommended), and 125MB free disk space on an Intel-based computer.

•  Minimum requirement for NT Server 4.0 on a RISC-based computer is 16MB RAM and 160MB free disk space.

•  RISC-based machines can be installed only from a SCSI CD-ROM.

•  Multiple copies of NT can be installed on the same partition provided they are in separate directories.

•  There is no automatic upgrade option from Windows 95 to NT 4.0; you must reinstall all common applications.

•  The BOOT.INI file is a text file that contains the operating system boot choices.

•  The BOOTSECT.DOS file contains the original boot sector code before NT is installed.

•  The logic might sound backward, but you boot from the system partition and system files are held on the boot partition.

•  The boot and system partitions can be the same.

•  WINNT32.EXE is used to upgrade when NT is already installed on the computer.

•  You can set up Intel-based computers using either a local CD-ROM or from over the network. Floppy disks are not an option in NT 4.0.

•  The minimum video configuration is VGA.

•  Passwords are case sensitive, user names are not.

•  You can create an NTHQ diagnostic disk by running MAKEDISK.BAT to test the system for compatibility.

•  RDISK is the repair disk utility. It is used to both create and update emergency repair disks.

•  The emergency repair disk is not bootable.

•  The NT Setup Manager is used to create hands-free installation scripts.

•  You use hands-free scripts with over-the-network setup by specifying the /b, /u, /udf, and /s switches.

•  The /udf switch is used with a file containing overrides to the unattended script file called with the /u switch.

•  The SYSDIFF.EXE utility is helpful for installing large numbers of systems with preinstalled software requirements.

•  TCP/IP and NWLink IPX/SPX-compatible transport are both routable protocols.

•  TCP/IP is the default protocol.

•  Automatic detection of network adapter cards locates only the first network card. Select the Find Next button to detect additional network cards. Only one card at a time is detected.

•  Computer names can be up to 15 characters and must be unique across the network.

•  NetBEUI is non-routable; it requires bridging.

3.2. Choosing the Right Equipment

As operating systems become more complex, the level of equipment required increases dramatically. You can personally cut corners to try to squeeze out a little more power for your money when purchasing your personal system. However, for purposes of the test, money is not the object; when choosing equipment, compatibility is the major criterion.

3.2.1. The Hardware Compatibility List (HCL)

The equipment that you use must be supported on the HCL. The latest copy of the HCL, shown in Figure 3.1, can be found at http://www.microsoft.com/hwtest/hcl or downloaded from ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/hcl/HCL40.

Figure 3.1.  Microsoft’s Web site provides the latest HCL information.

When troubleshooting a new system, one of the first things to confirm is that all of the equipment being used is supported on the HCL. The HCL contains listings of supported systems and accessories such as mice, SCSI cards, modems, network adapters, tape drives, and video cards.

NTHQ is an NT diagnostic tool that can help detect hardware conflicts. You create the bootable NTHQ disk by running makedisk.bat from the NT Server CD’s /support/hqtool directory. The NTHQ diagnostics are run automatically when you boot from the disk. Booting from the disk enables the utility to interact more closely with the hardware than diagnostics run from within NT.